home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.20041116-20060924
/
000326_fdc@columbia.edu_Tue May 2 12:10:11 2006.msg
< prev
next >
Wrap
Internet Message Format
|
2006-09-27
|
2KB
Path: newsmaster.cc.columbia.edu!not-for-mail
From: Frank da Cruz <fdc@columbia.edu>
Newsgroups: comp.protocols.kermit.misc
Subject: Re: output pacing questions
Date: 2 May 2006 11:37:03 GMT
Organization: Columbia University
Lines: 40
Message-ID: <slrne5eh2v.67g.fdc@sesame.cc.columbia.edu>
References: <qbD5g.1797$A26.49545@ursa-nb00s0.nbnet.nb.ca>
Reply-To: fdc@columbia.edu
NNTP-Posting-Host: sesame.cc.columbia.edu
X-Trace: newsmaster.cc.columbia.edu 1146569823 2509 128.59.59.56 (2 May 2006 11:37:03 GMT)
X-Complaints-To: postmaster@columbia.edu
NNTP-Posting-Date: 2 May 2006 11:37:03 GMT
User-Agent: slrn/0.9.8.0 (SunOS)
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:15583
On 2006-05-02, Scott Caissie <scottac@nb.sympatico.ca> wrote:
> Whats the default pacing speed? I'm guessing 1 millisecond.
>
Default is no pacing at all. If you "output foo" then "foo" is sent
as a string.
> Can I turn off the pre-check for pacing speed?
> When I increase this to a significant number such as 1000-2000 milliseconds,
> and try to output a string, it waits the full duration in COMMAND mode for
> the pacing. When I go to CONNECT mode, it takes an equal amount of time to
> output it. I have no problem with the last part. Its suppose to output at a
> certain speed that you specify.
> I just don't get why it does a pre-check on pacing.
>
> example:
> set output pacing 2000
> output testing123
> its gonna sit for 20 seconds before I get access to the prompt again. Then
> when I go to CONNECT mode, it will do the same thing. How do I turn off the
> pre-checking or whatever this is?
>
This doesn't sound to me like something it's supposed to do. The pacing
quantity is supposed to apply after each character of the OUTPUT string.
I did a quick check just now (on an SSH connection):
set output pacing 1000
output foo
This took exactly 3 seconds, as expected.
> The main goal was to do a very long task by checking anywhere from 10-200
> articles. I wanted it slow enough as to not cause any errors as to which
> screen it will be on. But the pre-check phase sorta scraped that idea
> entirely.
>
I guess I don't understand your application, but there are many ways to
synchronize things. The only purpose for OUTPUT PACING is to prevent data
overruns on connections that are not properly flow-controlled.
- Frank